-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use multiple CAs instead of a single self-signed root CA #327
base: humble
Are you sure you want to change the base?
Use multiple CAs instead of a single self-signed root CA #327
Conversation
Signed-off-by: Santti4go <[email protected]>
Signed-off-by: Santti4go <[email protected]>
Signed-off-by: Santti4go <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think these kind of new arguments or feature need to be supported in rolling 1st, and then we can consider backport for already released distros including humble.
Sure, I targeted Humble because it's the branch I'm working on. |
to be honest, i am not sure. having this optional mode seems to be okay but i do not really maintain this repository. @mikaelarguedas could you take a look or ping someone else here? |
Friendly ping @mikaelarguedas I've made a few more changes on my end. If we agree this is something we want to support I would happily push them here and target Rolling and then backport it. Let me know what you think. |
Ticket #328
I added a new (optional) flag for the
create_keystore
command:--split-CA
This flag changes the Certificate Authorities structure creating two new CAs (Permissions CA and Identity CA) instead of using the same self-signed root CA with symlinks.
This is an optional flag and does not change default behavior.
More details in the ticket #328
Note
I still need to sign both new CAs with root CA